feat: generate postgres user secret with r2dbc uris #3873
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Checklist:
Type of Changes:
What is the current behavior (link to any open issues here)?
The operator generates user secrets. For example if you use a r2dbc based application you cannot reference the jdbc-uri key from the secret.
What is the new behavior (if this is a feature change)?
r2dbc-uri keys are added to the secrets starting with
r2dbc:postgresql://....Other Information: